Skip to content

api: proxy: custom: Implement APIs for custom Go plugins #10299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 29, 2025

Conversation

cosmo0920
Copy link
Contributor

For some motivations to support custom plugin mechanism in Fluent Bit, we need to implement custom plugins which are built on top of Golang infrastructures.
This PR makes to be able to provide and support Golang custom plugins.
This PR is based on #9470 but adding modifications with working on calyptia-plugin module which is maintained here:

chronosphereio/calyptia-plugin#101

Plus, we need to implement custom plugin mechanism calyptia-plugin modue.
So, I also implemented custom Golang mechanism in chronosphereio/calyptia-plugin#101.

Note that we might have to maintain ABI for plugin API like logging and obtaining cmetrics instances.
I just adding APIs for custom plugins afterwards of input or output API definitions.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • Example configuration file for the change
  • Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@cosmo0920 cosmo0920 force-pushed the cosmo0920-go-custom-extension branch from d201c70 to e152ad2 Compare May 8, 2025 05:44
@cosmo0920 cosmo0920 force-pushed the cosmo0920-go-custom-extension branch from e152ad2 to 8d4db49 Compare May 8, 2025 05:45
@cosmo0920 cosmo0920 marked this pull request as ready for review May 8, 2025 08:11
cosmo0920 and others added 4 commits May 29, 2025 15:25
Signed-off-by: Rob Skillington <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>

Co-authored-by:  Rob Skillington <[email protected]>
Signed-off-by: Rob Skillington <[email protected]>
Signed-off-by: Hiroshi Hatake <[email protected]>

Co-authored-by: Rob Skillington <[email protected]>
@cosmo0920
Copy link
Contributor Author

I organaized commits for editing one group of files step-by-step way.
Plus, I added rob to refer his works with Co-authored-by lines.

@edsiper edsiper merged commit 538baad into master May 29, 2025
50 checks passed
@edsiper edsiper deleted the cosmo0920-go-custom-extension branch May 29, 2025 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants